Application data displayed through a selectable application icon

ABSTRACT

There are provided systems and methods for application data displayed through a selectable application icon. A computing device, such as a mobile smart phone, may include one or more processing application, such as a payment application to utilize an online payment provider. The application may include a desktop or folder icon, or other visual icon that may be presented within an interface of the device&#39;s operating system. Additionally, the application may include application data normally presented to the user of the device during operation of the application. The application or the device&#39;s operating system may select an informational element of the application information to present to the user. The informational element may then be presented on the application icon while the application is unopened or executing in the background of the operating system. Multiple informational elements may be cycled through on the application icon.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/968,730 filed on Dec. 14, 2015, the content of which is herebyincorporated by reference in its entirety for all purposes.

TECHNICAL FIELD

The present application generally relates to application icons and userinterfaces, and more specifically to application data displayed througha selectable application icon.

BACKGROUND

Computing devices may provide applications to users, which may allow theusers to execute certain processes and engage in various functionalitiesof the computing device. With the rise in mobile computing devices(e.g., mobile smart phones, tablet computers, etc.), users utilize moreand more specific dedicated applications for processes and functions.For example, a payment application may allow the users to provide mobileand/or digital payments. These payment applications may also includeadditional financial services, such as account balance updates,transaction review and dispute resolution, and credit history checks.The payment applications may interface with physical, real-worldmerchants nearby the user to allow the user to pay for transactions andpurchase items. Other popular applications may include messaging, email,social networking, and additional communication applications. Moreover,the merchants may provide their own dedicated application to alert theuser of sales and entice business. However, often such information isonly presented when the application is open and visibly displayed on adisplay device of the computing device. For example, the information maybe presented through an interface of the application currently ondisplay. Thus, if the user views the application icon when theapplication is closed or executing in the background of the device'soperating system, the user may be unaware of valuable informationassociated with the application.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a networked system suitable forimplementing the processes described herein, according to an embodiment;

FIG. 2A is an exemplary computing device interface having a customizedapplication icon presenting application information, according to anembodiment;

FIG. 2B is an exemplary computing device interface having a customizedapplication icon presenting application information, according to anembodiment;

FIG. 2C is an exemplary computing device interface for setup ofcustomized application icons using application information, according toan embodiment;

FIG. 2D is an exemplary computing device interface for setup ofcustomized application icons using application information, according toan embodiment;

FIG. 3 is an exemplary system environment showing a communication deviceof a user processing application data for an application to generate acustomized application icon having displayed application information,according to an embodiment;

FIG. 4 is a flowchart of an exemplary process for application datadisplayed through a selectable application icon, according to anembodiment; and

FIG. 5 is a block diagram of a computer system suitable for implementingone or more components in FIG. 1, according to an embodiment.

Embodiments of the present disclosure and their advantages are bestunderstood by referring to the detailed description that follows. Itshould be appreciated that like reference numerals are used to identifylike elements illustrated in one or more of the figures, whereinshowings therein are for purposes of illustrating embodiments of thepresent disclosure and not for purposes of limiting the same.

DETAILED DESCRIPTION

Provided are methods utilized for application data displayed through aselectable application icon. Systems suitable for practicing methods ofthe present disclosure are also provided.

A computing device for a user may include a display device, such as anoutput monitor, touch screen of a mobile phone that displays informationand interfaces to a user, or other type of visual output display device.The computing device may further include input devices, such as a mouse,keyboard, and/or touch screen able to detect touch inputs to the touchscreen. The device may be configured to execute one or more processesand/or functions, for example, through the use of an operating systemand associated device applications. In this regard, the device mayinclude one or more hardware processors to execute the processes and anon-transitory memory to store data used to execute the processes. Thus,the device's memory may store device applications, including payment,messaging, email, phone call, social networking, and/or merchantapplications.

Each application may be associated with application data, which may beutilized in the execution of the application. For example, applicationdata may include computer code utilized to cause the computing device toexecute the processes of the application and provide variousfunctionalities of the application. Thus, the application data mayinclude application interfaces, processes, and other associatedinformation used during the execution of the application. Theapplication data may include an application icon for the application,which may be displayable on an interface for an operating system of thecomputing device. The icon may include one or more graphical elements asa visual icon for display in the operating system's interface. Thegraphical elements may be designed so as to inform the user of theapplication. For example, the application icon may include graphicalelements that appear as a logo for a company associated with theapplication, a name of the application, a trademark associated with theapplication or a company providing the application, or other type ofelement that may inform the user of the application. The applicationicon may be displayable on a desktop or home screen of the device'soperating system, or may be displayable in a sub-folder, disk, or othervirtual storage area of the operating system. The application icon maybe selectable by the user so that selection of the application icon mayopen the application and cause the application to execute. In furtherembodiments where the application is already executing the background ofthe device's operating system, selection of the application icon maycall the application to the front of the operating system's interface todisplay the application's interface(s) on the output display screen ofthe computing device.

In this regard, the computing device may include a payment applicationas one of the device applications, which may be configured to send andreceive payments to another party, such as another user and/or amerchant. The payment application may be associated with a paymentprovider, such as PayPal® or other online payment provider service,which may provide payments and other financial services on behalf ofuser. The payment application may execute on the computing device forthe user, and may provide various functionalities and processes to theuser and/or merchant. For example, a user may utilize the paymentapplication to send and/or receive payments between the user and anotheruser/merchant. The user may wish to provide a payment for a transactionwith a user/merchant, transfer money to another family/friend, engage intransaction and statement review (e.g., financial dispute resolutionservices), or perform another financial transaction. Merchants maysimilarly use payment applications to send and/or receive paymentsbetween the merchant and another user/merchant, which may includereceiving payment for transactions, providing payments to employeesand/or for business expenses, transfer money between accounts, orperform further financial transactions. Other entities, such ascharitable organizations and businesses may also utilize the paymentapplication, for example, to receive donations from various partiesand/or pay business expenses. The online payment provider may providesuch services through the payment application and data sent and receivedover a network connection between the online payment provider and adevice executing the payment application. Additionally, the onlinepayment provider may provide payment accounts and digital walletservices, which may offer financial accounts to send, store, and receivemoney, process financial instruments, and/or provide transactionhistories. The online payment provider may offer further services, suchas extension of credit, credit history review, and other financial andpersonal services.

The payment application may therefore provide one or more processes andfeatures for use of the services provided by the online paymentprovider. The user of the computing device (e.g., a single or group ofusers, a merchant, or other entity) may cause the device to execute thepayment application by selecting the application, such as throughselection of the application icon. When utilizing the application, theapplication may execute in the foreground of the operating system andpresent application information to the user, such as a payment accountbalance or other status, pending and processed payments, receipts,transfer statuses, dispute, account information, and/or otherapplication information. Moreover, the application may execute in thebackground of the device's operating system and conduct processes whilethe user is otherwise using the device or has the device on butcurrently unused (e.g., a locked screen of a mobile smart phone). Whilethe application executes in the background, the various data may beprocessed, including data received from the online service providerand/or data sent to the online service provider (e.g., a location of theuser). When the application is closed, the device may still send data toand receive data from the online service provider, which may be storedto a database and presented to the user when the application is openedand an application interface displayed. In other embodiments, the userof the device may cause another application to execute, which mayinclude service, merchant, messaging, email, social networking, or otherapplication types. Such applications may process, send, and receiveother data as described above, including messages and email for a user,locations for the user and other users, nearby users, new statuses,merchant information (e.g., location, payment acceptance mechanisms,benefits and discounts, etc.), and other application information.

However, when the application is not open and an interface is operatingin the foreground of the operating system, the user may not be aware ofapplication information that may be relevant and useful to the user. Forexample, a recently processed transaction and a new account balance mayrequire the user to open the payment application and navigate to anaccount status interface to view the processed transaction, the amountdebited to the account, and the balance now available in the account.Other payment application information may also be displayable in aninterface of the application. Similarly, the payment application or amerchant application may be associated with a physical merchant locationat or nearby where the user is located, and may accept payments usingthe user's mobile device. However, the user may be required to open theapplication and view information on an interface to determine that themerchant accepts payments using the application executing on the mobiledevice.

In order to provide application information to a user without the userbeing required to open the application and view an applicationinterface, the payment application or another process or applicationexecuting on the device may determine at least one informational elementof the application information to present to the user. The informationalelement(s) may be selected by the payment application randomly or basedon various parameters. An application may generally display a mostimportant feature or informational element based on the application,application type, and/or processes of the application. For example, apayment application may wish to display a balance of an associatedpayment account to the user, as the balance may be the most important orrelevant to the user informational element of the applicationinformation. Other applications may include other important or relevantinformational elements, for example, mobile applications may wish toinform users of location specific information (e.g., tied to the user'scurrent location), social networking applications may wish to inform theuser of new statuses of friends or family, and messaging applicationsmay wish to display an unread message.

In various other embodiments, the user may set parameters andpreferences for informational elements the user may wish to view. Inthis regard, the application and/or the device's operating system mayallow the user to select preferences for the application (as well asother applications where the operating system configures theapplication) that determines application information to display to auser through the application icon. The preferences may include aselection of informational element(s) of the application information,including “display account balance,” “display new deposit amount,”“display daily balance change,” “display payment application acceptanceat location,” or other payment account related information for a paymentapplication. Other information may be request to be displayed for otherapplications, such as “display new message content,” “display nearbymerchants,” ‘display nearby offers,” or other information.

Additionally, the application may also determine the information todisplay based on newly received data and/or newly processed data. Forexample, if a new transaction is processed and the user's accountdebited, that informational element may be selected for display. Wherethe application finishes a process, the resulting processed data may beselected. In further embodiments, the information may be selected basedon an emergency, such as a potentially fraudulent transaction, a naturaldisaster, a traffic issue, a nearby crime or dangerous situation, afamily or friend emergency message or status, or other type of emergencysituation. In other embodiments, use of the application by the user maydetermine what informational element(s) is/are selected. Thus, theoperating system and/or the application may utilize the user's use ofthe application to determine what informational element(s) to display tothe user. For example, if the user's often uses a payment account toview an account balance, the account balance may be selected as theinformational element. Similarly, if the user often uses the paymentapplication to pay for items at physical merchant locations, whether theuser's current location accepts the payment application may bedisplayed, as well as a current outgoing payment amount, a daily accountbalance change, or other metric may be used. Thus, the applicationand/or operating system may intelligently learn the parts of theapplication that are most important or frequently used by the user, anddisplay an informational element related to the part of the applicationmost important or used by the user. Thus, the relevant metric may beselected by the device system.

Moreover, additional information may be used to determine whichinformational elements to display to a user and the content of theinformational element. As discussed above, a location of a user may beused to determine whether a merchant at the user's current locationaccepts payments made through the payment application (e.g., using anonline payment provider). Thus, the application and/or the operatingsystem may determine a location of the user, for example, using a GPSlocator or other location services component of the device. The locationmay then be used to determine relevant data, including acceptance of theapplication at the user's location, nearby merchants accepting paymentsthrough the payment application, and/or deals/offers for nearbymerchants. Where the application may correspond to another application,other data may be determined using the location, such as directions,nearby known users, etc. The informational element selected maycorrespond to the location, such as selection of merchant paymentacceptance mechanisms at the user's location where relevant instead of apayment account balance. However, where the informational element isalready selected based on other information or preferences, the locationmay be used to determine the content of the informational element, suchas whether the payment application is accepted for payments at thelocation. Additional data received or processed by the application mayalso be used to select the type and/or content of an informationalelement to display on the application, including biometrics of the user,messages and emails, or other accessible data. Additionally, in certainembodiments, multiple informational elements may be selected, which mayeach include separate application information. For example, the user mayset multiple preferences of information to display on the applicationicon, such as a balance, daily balance change, dispute status, etc. Inother embodiments, the application and/or operating system may determineeach of the multiple informational elements to display to the user, suchas through use of the application, important nearby information, orother available data.

In order to present the informational element(s) to the user without theapplication interfaces required to be open and/or presented on theforeground of the device's display screen, the application and/oroperating system and present the informational element(s) on or with theapplication icon for the application. For example, the informationalelement may be superimposed on top of the graphical element making upthe application icon (e.g., the logo, trademark, or other graphic usedas the application icon). Thus, the application icon may be processedwith the information element in order to display the informationalelement to the user through the application icon. The informationalelement may be presented on the application icon, for example, acrossthe top, bottom, or side of the graphical element for the icon. Theinformational element may be nearby and/or attached to the applicationicon, including in a corner, as a border, below, above, or otherwisenearby the application icon. The informational element may be presentedas text, numbers, and/or graphics. Additionally, the informationalelement may be color coded, font coded, or otherwise presented in anintuitive manner to the user. For example, account debits may include aminus (−) sign before and be presented in red font, while accountdeposits may include a plus (+) sign and a green font. Other graphicalrepresentations may also be used, such as a compass direction to anearby target, a flashing light indicating application acceptance as thelocation, etc.

The informational icon may be displayed prior to login to theapplication and/or opening the application. For example, the processesto present the informational element with the application icon mayexecute without the application being opened and/or currently executing(e.g., by the operating system) and may present the information on theapplication icon while the application is closed. The informationalelement on the icon may also be presented while the application isrunning but an interface of the application is not in the foreground ofthe operating system (e.g., the user if viewing a home screen orsub-folder of the operating system). Moreover, in certain embodiments,the user may set preference and/or the application may require the userto first open the application and/or login, for example, where theinformational element includes sensitive information. Additionally,where there are multiple informational elements, the process may scrollthrough the informational elements presented on the application icon,which may occur at preset or customizable intervals (e.g., present eachelement for 5 seconds). In various embodiments, the informationalelement may also be displayed within a banner or other icon badge on alock screen, home screen, dropdown menu, or other interface of theoperating system. For example, the user may elect to have a banner orbadge for the application and/or the application icon visible on a lockscreen or within a dashboard menu of the communication device. Thus, thecustomized application icon, banner, or badge displaying theinformational element may also be displayed on such an interface.

Selection of the application icon while an informational element ispresented may cause the application to immediately open to a window,interface, or process associated with the informational element. Forexample, if the application icon displays an account balance as theinformational element, selection of the application icon while theaccount balance is displayed may immediately open an interface for theaccount balance and statement history (e.g., past transactions using theaccount). Similarly, if the icon shows a processed payment, selection ofthe icon may bring an interface for the transaction, includingtransaction information for a time, place, merchant, etc. for thetransaction, an amount of the transaction, items in the transaction,and/or transaction dispute or cancellation option. Where multipleinformational elements may be scrolled through on the application icon,selection of the application icon when a specific informational elementis presented may cause the application to open to the window, interface,or processes associated with that specific informational element. Thus,the user may view the informational element and quickly navigate to theassociated application process when the informational element ispresented.

FIG. 1 is a block diagram of a networked system 100 suitable forimplementing the processes described herein, according to an embodiment.As shown, system 100 may comprise or implement a plurality of devices,servers, and/or software components that operate to perform variousmethodologies in accordance with the described embodiments. Exemplarydevices and servers may include device, stand-alone, andenterprise-class servers, operating an OS such as a MICROSOFT® OS, aUNIX® OS, a LINUX® OS, or other suitable device and/or server based OS.It can be appreciated that the devices and/or servers illustrated inFIG. 1 may be deployed in other ways and that the operations performedand/or the services provided by such devices and/or servers may becombined or separated for a given embodiment and may be performed by agreater number or fewer number of devices and/or servers. One or moredevices and/or servers may be operated and/or maintained by the same ordifferent entities.

System 100 includes a user (not shown), a communication device 110, amerchant server 130, and a payment provider server 140 in communicationover a network 150. The user may utilize communication device 110 toutilize the various features available for communication device 110,which may include processes and/or applications associated withcommunication device 110, merchant server 130, and/or payment providerserver 140. Communication device 110 may further be utilized to providepayments to one or more entities, such as other users and/or merchants(e.g., a merchant associated with merchant server 130), through anapplication executing on communication device 110. Various paymentprocesses and features may be executed using payment provider server140. Additionally, communication device 110 may be used to presentinformation elements for information presented to the user usingapplication icons for applications of communication device 110. Theinformational elements may be determined using merchant server 130and/or payment provider server 140.

Communication device 110, merchant server 130, and payment providerserver 140 may each include one or more processors, memories, and otherappropriate components for executing instructions such as program codeand/or data stored on one or more computer readable mediums to implementthe various applications, data, and steps described herein. For example,such instructions may be stored in one or more computer readable mediasuch as memories or data storage devices internal and/or external tovarious components of system 100, and/or accessible over network 150.

Communication device 110 may be implemented as a communication devicethat may utilize appropriate hardware and software configured for wiredand/or wireless communication with merchant server 130, and/or paymentprovider server 140. For example, in one embodiment, communicationdevice 110 may be implemented as a personal computer (PC), telephonicdevice, a smart phone, laptop/tablet computer, wristwatch withappropriate computer hardware resources, eyeglasses with appropriatecomputer hardware (e.g. GOOGLE GLASS®), other type of wearable computingdevice, implantable communication devices, and/or other types ofcomputing devices capable of transmitting and/or receiving data, such asan IPAD® from APPLE®. Communication device 110 may execute a variety ofapplications, including payment and other mobile applications. Althoughonly one communication device is shown, a plurality of communicationdevices may function similarly.

Communication device 110 of FIG. 1 contains a device application 120, apayment application 112, other applications 114, a database 116, and acommunication module 118. Touch interface component 120, deviceapplication 120, payment application 112, and other applications 114 maycorrespond to executable processes, procedures, and/or applications withassociated hardware. In other embodiments, communication device 110 mayinclude additional or different modules having specialized hardwareand/or software as required.

Device application 120 may correspond to one or more processes toexecute software of communication device 110, including execution of anoperating system for communication device 110 or an applicationexecutable by communication device 110 using an operating system ofcommunication device 110. In this regard, device application 120 maycorrespond to specialized hardware and/or software utilized bycommunication device 110 to provide processes and features to a userutilizing communication device 110. In various embodiments, deviceapplication 120 may correspond to an operating system, which may includesystem software that manages and controls hardware and softwareresources of communication device 110. The operating system may providea set of services to the user of communication device 110, includingaccess of various device hardware and software features, management ofdevice resources, and data processing. The services may be commonly usedby applications of communication device 110. Thus, additionalapplications and programs may require the operating system to function,where the operating system may assist communication device 110 withexecuting code-able processes. The operating system may further provideadditional functions, such as receiving and processing input, outputtingdata to a user through one or more output devices (e.g., displays,speakers, etc.), processor management and process allocation, and memorymanagement and allocation. The operating system and correspond to amobile device, tablet computer, or home computing device. Where deviceapplication 120 functions as an operating system, device application 120may provide processing of application icons to present informationalelements, as discussed herein.

In other embodiments, device application 120 may correspond to anapplication for execution by communication device 110 through anoperating system. For example, device application 120 may correspond toa social networking, messaging, email, media playback, camera,image/video, or other type of device application. Device application 120may include application data, including an application icon having agraphical element. The application data may further include applicationinformation, such as received and/or processed data for deviceapplication 120. Such application information may include one or moreinformational elements to presentation to a user through the applicationicon for device application 120, as discussed herein. Thus, theoperating system and/or device application 120 may determine theinformational element(s) and process the application icon to present theinformational element(s) to the user through the application icon.

Payment application 112 may correspond to one or more processes toexecute software modules and associated devices of communication device110 to enter one or more payment instruments or other funding sourcesfor storage in a digital wallet associated with a payment account (e.g.,stored and/or serviced by payment provider server 140), access thedigital wallet and/or payment account for use, and provide payments toanother entity. In this regard, payment application 112 may correspondto specialized hardware and/or software utilized by a user ofcommunication device 110 that provides an interface to permit the userto enter input and other data for payment instruments, for example,through an input device (e.g., touch screen with a graphical userinterface displayed by payment application 112, keypad/keyboard, mouse,etc.) and/or through a data capture device (e.g., scanner, camera, otheroptical device, etc.) In various embodiments, information for thepayment account may also be stored to communication device 110 for usein an offline environment. The payment account accessible throughpayment application 112 may be used to initiate, receive, and/orprocess/complete transactions using services provided by paymentprovider server 140. Once entered, the payment instruments may becommunicated to payment provider server 140 over network 150 by paymentapplication 112 for establishment and/or maintenance/update of thepayment account and/or entry into the digital wallet. The user ofcommunication device 110 may also enter benefits to payment application112. The benefits may correspond to one or more of rewards programs,rewards programs membership level, rewards program points, availableitems in at least one rewards program, cash-back amounts for the atleast one rewards program, airline miles, promotional credit,promotional credit rates, promotional discount rate, merchant discounts,merchant discount rates, and merchant coupons.

Payment application 112 may be implemented as a user interface enablingthe user to select and provide payment. In various embodiments, paymentapplication 112 may include a general browser application configured toretrieve, present, and communicate information over the Internet (e.g.,utilize resources on the World Wide Web) or a private network. Forexample, payment application 112 may provide a web browser, which maysend and receive information over network 150, including retrievingwebsite information (e.g., a website for payment provider server 140),presenting the website information to the user, and/or communicatinginformation to the website, including payment information for paymentthrough payment provider server 140. However, in other embodiments,payment application 112 may include a dedicated application of paymentprovider server 140 or other entity (e.g., a merchant), which may beconfigured to assist in processing purchase requests.

Payment application 112 may be utilized to select payment instrument(s)for use during in providing payment for a transaction, transfer, orother financial process. As discussed herein, payment application 112may utilize user financial information, such as a credit card, bankaccount, or other financial account, as a payment instrument whenproviding payment information. Additionally, payment application 112 mayutilize a user account with payment provider, such as payment providerserver 140, as the payment instrument. Selection of a payment instrumentmay occur prior to, at, or after establishment of the financial process.Payment provider server 140 may then use the payment instrument duringprocessing of payment, as discussed herein with respect to paymentprovider server 140. Payment application 112 may be utilized to view theresults of payment, for example, using transaction histories, disputeresolution processes, and other post-transaction process.

Device application 120, payment application 112, and/or an operatingsystem of communication device 110 may include application iconprocesses used to present application information to a user through anapplication icon for the application corresponding to the applicationinformation. In this regard, the application icon processes executed byone of device application 120, payment application 112, and/or anoperating system of communication device 110 may first determine atleast one informational element of application data to display to theuser through the application icon. The application icon processes mayautomatically and generally include an informational element selected tobe displayed to a user, such as a default informational element, whichmay be static or changeable by the user of communication device 110. Forexample, payment application 112 may generally default to selecting anaccount balance informational element to present to a user. Similarly,the operating system of communication device 110 may determine that anapplication is directed to a certain subject and/or that certaininformation is used by the application, and select informationelement(s) tied to that subject and/or used information for display. Inother embodiments, the informational element may be a most importantinformational element, which may be general for device application 120and/or payment application 112, or specific to current data accessiblefor communication device 110. For example, a general useful informationelement for payment application 112 may include an account balance, arecent transaction debit/credit, and/or a daily balance change. Thus,the application icon processes may select any of the aforementionedinformational elements for presentation to the user. However, whereother data is available, such as a location, biometric, message, etc.,the application icon processes may select a more specific informationalelement considered to be important or useful, such as acceptance ofpayment application 112 at a location.

Thus, in various embodiments, additional information accessible tocommunication device 110 may be used to determine an informationalelement to display to the user of communication device 110. A locationof a user may be determined using a GPS locator or other locationservices component of the device. Using the location, the applicationicon processes may determine associated data, such as nearby merchantsoffering deals and benefits to the user, acceptance of paymentapplication 112 for payments, nearby friends, directions, etc. Theapplication icon processes may then determine an information element forthe relevant information for the location, and may determine content todisplay to the user based on the location (e.g., an “accepted here”message for merchant locations accepting payment application 112). Othertypes of associated data used to determine an informational element bythe application icon processes may include biometrics of the user,messages and emails, social networking posts, locations of otherfriends/family/merchants, available media, or other accessible data.

In other embodiments, the informational element selected by theapplication icon processes may include recently received or processeddata for device application 120 and/or payment application 112. Recentlyreceived data may include data from payment provider server 140, such asa new debit/credit to an account, a dispute resolution or other status,a processed transaction, a transfer, a transaction status, merchantinformation for nearby merchants, etc. Additionally, device application120 may receive merchant information, sales, offers, locations, andother data from merchant server 130. Device application 120 may alsoreceive other application related data corresponding to the function andprocesses of device application 120, including messages, emails, socialnetworking status, available media, etc. In various embodiments, anotherapplication's information may cause selection of the informationalelement. For example, information for a recent email may be added to acontact list, where a message that a contact has been added or updatedmay be presented as the informational element on a contact list icon.

In various other embodiments, the user may set parameters andpreferences for informational elements the user may wish to view. Inthis regard, device application 120, payment application 112, and/orcommunication device 110's operating system may allow the user to selectpreferences for the informational element an application displays on theapplication's icon. For example, a setup and/or configuration screen maybe used to establish the preferences of what application information auser would like to see “before login” or “on the application icon.” Theuser may select one or more options of the information element type,name, or other identifier, which may cause the informational elementassociated with that selection from the application information to bedisplayed on the application icon for the application.

In other embodiments, device application 120, payment application 112,and/or communication device 110's operating system may intelligentlyselect the information element based on use of the application by theuser. For example, if the user often checks an account balance inpayment application 112 and/or uses payment application 112 forreal-world purchases at physical merchant locations, one or moreinformational elements associated with this use may be selected. Wheredevice application 120 is used to execute a certain process, one or moreinformational elements having data presentable to the user for thisprocess may also be selected. The application icon processes of deviceapplication 120, payment application 112, and/or communication device110's operating system may review use of the application bycommunication device 110's user and may update or change the presentableinformational element based on changes in use. Thus, the applicationand/or operating system may intelligently learn the parts of theapplication that are most important or frequently used by the user,determine the relevant metric, and present the metric as aninformational element to the user.

The application icon processes may select a single informational elementusing the aforementioned processes, or may select multiple informationalelements from the application information. Such selection may be doneautomatically by the application icon processes, or may be made based onpreferences set by the user. For example, the user may set multiplepreferences of information to display on the application icon, such as abalance, daily balance change, dispute status, etc. In otherembodiments, the application and/or operating system may determine eachof the multiple informational elements to display to the user, such asthrough use of the application, important nearby information, or otherprocess as described herein.

Presentation of the selection informational element(s) by theapplication icon processes may occur through the application icon fordevice application 120 and/or payment application 112. The applicationicon may include one or more graphics, or graphical elements/featuresthat are used to visually represent the application and allow the userto easily identify the application (e.g., through association of thegraphical elements with the application). Thus, the graphical elementsmay include a trademark, such as a logo, symbol, name, or otheridentifier for the application. Other graphical elements may includecharacters, application images, text, etc., which may visually representthe application. The informational element(s) may then be superimposedon top of the graphical element(s), which may be placed in the center,bottom, side, or other area of the application icon. In otherembodiments, the informational element may surround, be located on acorner, above, below, or otherwise act as a border to the applicationicon. The informational element(s) may be presented as text, numbers,and/or graphics, and may including colors, fonts, or other features. Thefeatures of the informational element(s) may be coded in order to allowthe user to easily decipher the information of the informationalelement. For example, red color may be used for debits, missed messages,or emergencies. Similarly, green color may be used for deposits,potential savings, etc. Other graphical representations may also beused, such as a compass direction to a nearby target, a flashing lightindicating application acceptance as the location.

Thus, a customized application icon may be generated having theinformational element(s) presented with the application icon's graphicalelements and features. The customized icon with the informationalelements may be displayed prior to login to the application and/oropening the application, for example, without the application beingopened and/or currently executing. In other embodiments, theinformational element may only be presented on the application icon whenthe application is executing, but may be in a background of theoperating system and not currently open in the foreground interface.Moreover, certain informational elements may only be presented after alogin or authentication, for example, where the informational elementincludes sensitive information or the user has set a preferencerequiring authentication. Additionally, where there are multipleinformational elements, the process may scroll through the informationalelements presented on the application icon, which may occur at preset orcustomizable time intervals.

Selection of the application icon while an informational element ispresented may cause the application to immediately open to a window,interface, or process associated with the informational element. Forexample, payment application 112's application icon may display acurrent balance or a received payment/credit to an account of the userand used by payment application 112. Thus, selection of the applicationicon for payment application 112 during presentation of one of theseinformational elements may open a corresponding webpage, interface,window, or other process that is associated with that informationalelement. Where multiple informational elements are scrolled through onthe application icon, this may allow the user to quickly navigate to anyof the associated processes by selecting the application icon when thedesired informational element is displayed with the application icon.

One or more of the aforementioned features and/or processes of deviceapplication 120 may be included within payment application 112 or viceversa, for example, to provide their respective features within oneapplication and/or application interface.

In various embodiments, communication device 110 includes otherapplications 114 as may be desired in particular embodiments to providefeatures to communication device 110. For example, other applications114 may include security applications for implementing client-sidesecurity features, programmatic client applications for interfacing withappropriate application programming interfaces (APIs) over network 150,or other types of applications. Other applications 114 may also includeemail, texting, voice and IM applications that allow a user to send andreceive emails, calls, texts, and other notifications through network150. In various embodiments, other applications 114 may includefinancial applications, such as banking applications. Other applications114 may also include other location detection applications, which may beused to determine a location for the user, such as a mapping, compass,and/or GPS application, which can include a specialized GPS receiverthat obtains location information for communication device 110 andprocesses the location information to determine a location ofcommunication device 110 and the user. Other applications may includesocial networking applications, media viewing, and/or merchantapplications. Other applications 114 may include device interfaces andother display modules that may receive input from the user and/or outputinformation to the user. For example, other applications 114 may containsoftware programs, executable by a processor, including a graphical userinterface (GUI) configured to provide an interface to the user. Otherapplications 114 may therefore use device components of communicationdevice 110, such as output display devices capable of displayinginformation to users and other output devices, including speakers.

Communication device 110 may further include database 116 stored to atransitory and/or non-transitory memory of communication device 110,which may store various applications and data and be utilized duringexecution of various modules of communication device 110. Thus, database116 may include, for example, identifiers such as operating systemregistry entries, cookies associated with payment application 112 and/orother applications 114, identifiers associated with hardware ofcommunication device 110, or other appropriate identifiers, such asidentifiers used for payment/user/device authentication oridentification, which may be communicated as identifying communicationdevice 110 to payment provider server 140. Database 116 may includeapplication data for an application, such as application icon data andapplication information used during the execution of an application.Additionally, customized application icons and/or selected informationalelements for an application may be stored to database 116.

Communication device 110 includes at least one communication module 118adapted to communicate with merchant server 130 and/or payment providerserver 140. In various embodiments, communication module 118 may includea DSL (e.g., Digital Subscriber Line) modem, a PSTN (Public SwitchedTelephone Network) modem, an Ethernet device, a broadband device, asatellite device and/or various other types of wired and/or wirelessnetwork communication devices including microwave, radio frequency,infrared, Bluetooth, and near field communication devices. Communicationmodule 118 may communicate directly with nearby devices using shortrange communications, such as Bluetooth Low Energy, LTE Direct, WiFi,radio frequency, infrared, Bluetooth, and near field communications.

Merchant server 130 may be implemented using any appropriate hardwareand software configured for wired and/or wireless communication withcommunication device 110 and/or payment provider server 140. Althoughdescribed below as a server, merchant server 130 may correspond to adevice, server, or cloud computing architecture to provide sales ofitems, for example, through an online marketplace accessible over anetwork connection with merchant server 130 and/or a physical merchantlocation. Merchant server 130 may further be used to process paymentsfor items and provide incentives for purchase of items and/oradvertisement of items to other users. Although only one merchant serveris shown, a plurality of merchant servers may function similarly.

Merchant server 130 of FIG. 1 contains a merchant application 132, otherapplications 134, a database 136, and a communication module 138.Merchant application 132 and other applications 134 may correspond toprocesses, procedures, and/or applications executable by a hardwareprocessor, for example, a software program. In other embodiments,merchant server 130 may include additional or different modules havingspecialized hardware and/or software as required.

Merchant application 132 may correspond to one or more processes toexecute modules and associated specialized hardware of merchant server130 that provides an interface and/or online marketplace to sell one ormore items offered by a merchant (not shown) associated with merchantserver 130, and further provide checkout and payment processes for atransaction to purchase the items for sale from the merchantcorresponding to merchant server 130. In this regard, merchantapplication 132 may correspond to specialized hardware and/or softwareof merchant server 130 to provide a convenient interface to permit amerchant offer items for sale. For example, merchant application 132 maybe implemented as an application offering items for sale that may beutilized by the merchant or a merchant employee to enter items selectedby a user to a transaction, determine a price for the transaction, andinitiate a checkout and payment process for the transaction. In otherembodiments, merchant application 132 may be accessed by communicationdevice 110 to select the items for sale to the user associated withcommunication device 110. In certain embodiments, merchant application132 may correspond to a website available over the Internet and/oronline content and/or database information accessible through adedicated application. Thus, sales module 160 may provide item salesthrough an online marketplace using the website of the merchant.However, in other embodiments, merchant server 130 may be local to aphysical merchant location and provide transaction processing processesthrough interfaces displayed to a merchant or merchant employee at themerchant location.

Merchant application 132 may include information for a price for theitem, a discount for the item, a price change for the item, and/or otherincentives for items and/or with the merchant corresponding to merchantserver 130 (e.g., rebates, payments, etc.). Merchant application 132 maybe used to set and/or determine a benefit or incentive provided to auser of communication device 110. The sales data and other item data maybe retrievable by communication device 110 and/or payment providerserver 140, such as requestable through an API call, retrievable from adatabase, and/or scraped from an online resource. The information may bebased updated periodically or continuously, such as in real time andinformation for the item(s) for sale changes. Merchant application 132may also include merchant information, such as a merchant location,payment mechanisms accepted by the merchant, and other relevant data fora merchant. Communication device 110 may receive and/or request themerchant information, for example, when determining an informationalelement to present to a user on an application icon.

Merchant application 132 may be used to establish a transaction once theuser associated with communication device 110 has selected one or moreitems for purchase. Once a payment amount is determined for thetransaction for the item(s) to be purchased, merchant application 132may request payment from the user. Merchant application 132 may receivepayment processing information, such as a payment and a receipt. In suchembodiments, the payment request may be processed, payment provided tothe merchant account, and notification of payment (or failure, forexample, where there are insufficient user funds) may be sent tomerchant application 132. The payment may be made by payment providerserver 140 on behalf of the user associated with communication device110. Merchant application 132 may then receive the results of thetransaction processing, and complete the transaction with the user, forexample, by providing the user the items for the transaction ordeclining the transaction where the user is not authenticated or thetransaction is not authorized (e.g., insufficient funds).

Merchant server 130 includes other applications 134 as may be desired inparticular embodiments to provide features to merchant server 130. Forexample, other applications 134 may include security applications forimplementing server-side security features, programmatic clientapplications for interfacing with appropriate application programminginterfaces (APIs) over network 150, or other types of applications.Other applications 134 may also include email, texting, voice and IMapplications that allow a user to send and receive emails, calls, texts,and other notifications through network 150. In various embodiments,other applications 134 may include financial applications, such asbanking, online payments, money transfer, or other applicationsassociated with payment provider server 140. Other applications 134 maycontain software programs, executable by a processor, including agraphical user interface (GUI) configured to provide an interface to theuser.

Merchant server 130 may further include database 136 which may include,for example, identifiers such as operating system registry entries,cookies associated with merchant application 132 and/or otherapplications 134, identifiers associated with hardware of merchantserver 130, or other appropriate identifiers, such as identifiers usedfor payment/user/device authentication or identification. Identifiers indatabase 136 may be used by a payment/credit provider, such as paymentprovider server 140, to associate merchant server 130 with a particularaccount maintained by the payment/credit provider. Merchant, item,sales, and/or benefit information for items sold by the merchantassociated with merchant server 130 may be stored to database 136.Database 136 may further include transaction information and/or results,including transaction histories.

Merchant server 130 includes at least one communication module 138adapted to communicate with communication device 110 and/or paymentprovider server 140. In various embodiments, communication module 138may include a DSL (e.g., Digital Subscriber Line) modem, a PSTN (PublicSwitched Telephone Network) modem, an Ethernet device, a broadbanddevice, a satellite device and/or various other types of wired and/orwireless network communication devices including microwave, radiofrequency, infrared, Bluetooth, and near field communication devices.

Payment provider server 140 may be maintained, for example, by an onlineservice provider, which may provide payment and financial services to auser. In this regard, payment provider server 140 includes one or moreprocessing applications which may be configured to interact withcommunication device 110, merchant device 150, and/or anotherdevice/server to provide transaction processing, account services, andother financial processes. In one example, payment provider server 140may be provided by PAYPAL®, Inc. of San Jose, Calif., USA. However, inother embodiments, payment provider server 140 may be maintained by orinclude another type of service provider, which may provide connectionservices to a plurality of users.

Payment provider server 140 of FIG. 1 includes a transaction processingapplication 142, other applications 144, a database 146, and a networkinterface component 148. Transaction processing application 142 andother applications 144 may correspond to executable processes,procedures, and/or applications with associated hardware. In otherembodiments, payment provider server 140 may include additional ordifferent modules having specialized hardware and/or software asrequired.

Transaction processing application 142 may correspond to one or moreprocesses to execute software modules and associated specializedhardware of payment provider server 140 to provide payment services tomerchants and users, for example though a payment account and/or paymentinstruments. In this regard, transaction processing application 142 maycorrespond to specialized hardware and/or software to provide paymentservices and payment accounts, including digital wallets storing paymentinstruments. The payment services may allow for a payment to themerchant by a user through a payment instrument, including acredit/debit card, banking account, payment account with paymentprovider server 140, and/or other financial instrument. In order toestablish a payment account for a merchant and/or user to send andreceive payments, transaction processing application 142 may receiveinformation requesting establishment of the payment account. Theinformation may include user personal and/or financial information.Additionally the information may include a login, account name,password, PIN, or other account creation information. The merchant/usermay provide a name, address, social security number, or other personalinformation necessary to establish the account and/or effectuatepayments through the account. Transaction processing application 142 mayfurther allow the merchant/user to service and maintain the paymentaccount, for example, by adding and removing payment instruments.Various information associated with the payment account, such as anaccount balance, transaction dispute status, pending payment, accountchange, pending credit, processed payment/credit, or other accountinformation may be pushed to communication device 110, for example, toprovide customized application icons presenting the aforementionedinformation, and/or pulled by communication device 110.

Transaction processing application 142 may be used to provide a paymentfor an item to a merchant, for example, between communication device 110and merchant server 130 (e.g., using touch inputs with communicationdevice 110 to effectuate the payment). Transaction processingapplication 142 may debit an account of the user automatically andprovide the payment to an account of the merchant. Transactionprocessing application 142 may also be used to provide transactionhistories for processed transactions. Based on the transactionprocessing, transaction data may be pushed to communication device 110and/or pulled by communication device 110. The transaction informationmay be used by communication device 110 to select informational elementsto present to a user and customize application icons using theinformational elements.

In various embodiments, payment provider server 140 includes otherapplications 144 as may be desired in particular embodiments to providefeatures to payment provider server 134. For example, other applications144 may include security applications for implementing server-sidesecurity features, programmatic client applications for interfacing withappropriate application programming interfaces (APIs) over network 150,or other types of applications. Other applications 144 may containsoftware programs, executable by a processor, including a graphical userinterface (GUI), configured to provide an interface to the user whenaccessing payment provider server 140, where the user or other users mayinteract with the GUI to more easily view and communicate information.In various embodiments, other applications 144 may include connectionand/or communication applications, which may be utilized to communicateinformation to over network 150.

Additionally, payment provider server 140 includes database 146. Aspreviously discussed, the user and/or the merchant corresponding totelecommunication carrier server 170 may establish one or more digitalwallets and/or payment accounts with payment provider server 140.Digital wallets and/or payment accounts in database 146 may include userinformation, such as name, address, birthdate, paymentinstruments/funding sources, additional user financial information, userpreferences, and/or other desired user data. Users may link to theirrespective digital wallets and/or payment accounts through an account,user, merchant, and/or device identifier. Thus, when an identifier istransmitted to payment provider server 140, e.g. from communicationdevice 110, one or more digital wallets and/or payment accountsbelonging to the users may be found. Database 146 may also store theuser preferences for an account for the user and/or merchant.

In various embodiments, payment provider server 140 includes at leastone network interface component 148 adapted to communicate communicationdevice 110 and/or merchant server 130 over network 150. In variousembodiments, network interface component 148 may comprise a DSL (e.g.,Digital Subscriber Line) modem, a PSTN (Public Switched TelephoneNetwork) modem, an Ethernet device, a broadband device, a satellitedevice and/or various other types of wired and/or wireless networkcommunication devices including microwave, radio frequency (RF), andinfrared (IR) communication devices.

Network 150 may be implemented as a single network or a combination ofmultiple networks. For example, in various embodiments, network 150 mayinclude the Internet or one or more intranets, landline networks,wireless networks, and/or other appropriate types of networks. Thus,network 150 may correspond to small scale communication networks, suchas a private or local area network, or a larger scale network, such as awide area network or the Internet, accessible by the various componentsof system 100.

FIG. 2A is an exemplary computing device interface having a customizedapplication icon presenting application information, according to anembodiment. Environment 200 a includes a communication device 110corresponding generally to the described features, processes, andcomponents of communication device 110 in environment 100 of FIG. 1. Inthis regard, a user utilizing communication device 110 may view aninterface 1000 on communication device 110, where interface 1000corresponds to an interface of a payment application, such as paymentapplication 112 of communication device 110 in environment 100 of FIG.1.

Interface 1000 displays a screen of an operating system of communicationdevice 110, which may display a customized application icon displayingan informational element of an application on communication device 110.For example, interface 1000 includes a money window 1002 correspondingto an operating system folder window having financial applications ofcommunication device 110. For example, application icons 1004 may eachcorrespond to a financial application. Application icon 1006 maycorrespond to a specific financial application associated with an onlinepayment provider. For example, a graphical element 1008 is displayed forthe online payment provider. Moreover, an informational element 1010 isshown displayed on application 1006 by presenting informational element1010 on application icon 1006 and with graphical element 1008. Thus,application icon 1006 is shown as customized with informational element1010 shown with graphical element 1008 to allow a user to view anaccount balance ($1,234.54) for an account used by the applicationcorresponding to application icon 1006.

FIG. 2B is an exemplary computing device interface having a customizedapplication icon presenting application information, according to anembodiment. Environment 200 b includes a communication device 110corresponding generally to the described features, processes, andcomponents of communication device 110 in environment 100 of FIG. 1. Inthis regard, a user utilizing communication device 110 may view aninterface 1100 on communication device 110, where interface 1100corresponds to an interface of a payment application, such as paymentapplication 112 of communication device 110 in environment 100 of FIG.1.

Environment 200 b includes a similar interface layout of communicationdevice 110 to that of environment 200 a. Thus, interface 1100 includes amoney window 1102 for a similar operating system window havingapplication icons 1104. An application icon 1106 for the online paymentprovider is again shown with a graphical element 1008 for the onlinepayment provider. However, in environment 200 b, an informationalelement 1110 instead corresponds to a new deposit received to theaccount of the user with the online payment provider. Thus,informational element 1110 instead shows +$120.22. Informational element1110 may be selected to be presented on application icon 1006 based onuser preferences, and may either update informational element 1010 fromenvironment 200 a or be chosen based on user preference, application useby the user, or other selection parameter.

FIG. 2C is an exemplary computing device interface for setup ofcustomized application icons using application information, according toan embodiment. Environment 200 a includes a communication device 110corresponding generally to the described features, processes, andcomponents of communication device 110 in environment 100 of FIG. 1. Inthis regard, a user utilizing communication device 110 may view aninterface 1200 on communication device 110, where interface 1200corresponds to an interface of a payment application, such as paymentapplication 112 of communication device 110 in environment 100 of FIG.1.

Environment 200 c shows an exemplary application and/or operating systeminterface used to set up and establish informational elements to presenton an application icon. For example, interface 1200 includes userinformation 1202 for an application, such as the payment applicationcorresponding to application icon 1006 and 1106 in environment 200 a andenvironment 200 b, respectively. Interface 1200 includes account setting1204 and application settings 1210. In order to establish informationalelements presented on an application icon and other application iconnotifications, interface 1200 further includes notification settings1206. Within notifications settings 1206 include home screen iconsettings 1208. Selection of home screen icon settings 1208 may load aninterface 1300 shown in environment 200 d of FIG. 2D.

FIG. 2D is an exemplary computing device interface for setup ofcustomized application icons using application information, according toan embodiment. Environment 200 a includes a communication device 110corresponding generally to the described features, processes, andcomponents of communication device 110 in environment 100 of FIG. 1. Inthis regard, a user utilizing communication device 110 may view aninterface 1300 on communication device 110, where interface 1300corresponds to an interface of a payment application, such as paymentapplication 112 of communication device 110 in environment 100 of FIG.1.

Interface 1300 includes information used to establish informationalelements presented on an application icon. Thus, a menu selection 1302allows selection of information to display on an application elementprior to opening the application. Options 1304 allow selection ofvarious informational elements to display to the user on the applicationicon for the corresponding application. For example, options 1304includes “available balance,” “disputes,” “orders,” “performance dayover day,” “performance week over week,” “performance month over month,”and “performance year over year.” Each of options 1304 may be selectedby a user. For example, “available balance” is shown as selected option1306, which can be shown displayed on application icon 1006 ofenvironment 200 a as informational element 1010.

FIG. 3 is an exemplary system environment showing a communication deviceof a user processing application data for an application to generate acustomized application icon having displayed application information,according to an embodiment. FIG. 3 includes communication device 110,merchant server 130, and a payment provider server 140 all discussed inreference to environment 100 of FIG. 1.

Communication device 110 executes payment application 112 correspondinggenerally to the specialized hardware and/or software modules andprocesses described in reference to FIG. 1. In this regard, paymentapplication 112 may include information used to determine customizedapplication icons displaying informational elements for applicationinformation. Thus, payment application 112 includes application data2000 for an application. Application data 2000 includes an applicationicon 2002 having graphical elements 2004 and display information 2006for display of application icon 2002 to a user through a graphical userinterface. Application data 2000 further includes applicationinformation 2008 for display to a user and interaction with the userduring use of the application. Application information 2008 may includean account status 2010 for an account (e.g., a payment account),financial transactions 2012, and/or additional information 2014.Additional data stored to application data 2000 may include processes2016 for execution by the application, user preferences 2018 ofapplication information 2008 to display to a user using application icon2002, user information 2020 used to select application information 2008for display, and/or application use 2022 used to select applicationinformation 2008 for display. In various embodiments, paymentapplication 112 further includes customized icon 2024 once generatedusing a selected informational element from application information2008, which may include selected information 2026, display process 2028,selection data 2030, and a displayable icon 2032.

Merchant server 130 executes merchant application 132 correspondinggenerally to the specialized hardware and/or software modules andprocesses described in reference to FIG. 1. In this regard, merchantapplication 132 may be used to establish and/or process a transactionbetween communication device 110 and merchant server 130, and provideitem and merchant information to communication device 110 for generationof customized icon 2024. Thus, merchant application 132 includesmerchant information 2100. Merchant information 2100 may includemerchant, item, sales, and/or benefit information for a merchantcorresponding to merchant server 130. For example, merchant information2100 includes sales data 2102 for one or more items and merchant data2104 for the merchant. Merchant data 2104 may include a merchantlocation 2106 and payment processes 2108 accepted by the merchant atmerchant location 2106.

Payment provider server 140 executes transaction processing application142 corresponding generally to the specialized hardware and/or softwaremodules and processes described in reference to FIG. 1. In this regard,transaction processing application 142 may be used to process atransaction between communication device 110 and merchant server 130 andprovide payment accounts to users, which may include informationpresented in payment application 112. For example, transactionprocessing application 142 includes payment accounts 2200 for users,which may include a payment account A 2202 for the user of communicationdevice 110. Payment account A 2202 includes application information 2008used by payment application 112, as well as new data 2204, which may becommunicated to communication device 110. In various embodiments,transaction processing application 142 further includes transaction 2206processed by payment provider server 140.

FIG. 4 is a flowchart of an exemplary process for application datadisplayed through a selectable application icon, according to anembodiment. Note that one or more steps, processes, and methodsdescribed herein may be omitted, performed in a different sequence, orcombined as desired or appropriate.

At step 402, first application data for a first application executableby the computing device system is accessed by a computing device systemthat comprises one or more hardware processors coupled to anon-transitory memory, wherein the first application data comprises afirst application icon for the first application and first applicationinformation displayed to a user of the computing device system duringuse of the first application, and wherein the first application iconcomprises a first graphical element associated with the firstapplication. The first application may comprise a payment applicationfor an online payment provider, wherein the first graphical elementcomprises a logo of the online payment provider. The first applicationicon may be displayed on a home screen interface of an operating systemof the computing device system. For example, the computing device systemmay comprise a mobile phone device, wherein the first applicationcomprises a mobile application of the mobile phone device.

At least one first informational element from the first applicationinformation for display to the user on the first application icon of thefirst application is determined, at step 404. The at least one firstinformational element may comprise at least one of an account balance ofan account for the user with the online payment provider, a disputehistory for the account, a new payment received to the account, a newdebit to the account, a new transfer using the account, a pending orderstatus of the user using the account, and a pending payment status tothe account. In other embodiments, the at least one first informationalelement may comprise a financial status, a new message, a new email,phone message information, stock information for a financial investmentof the user, and a social networking connection. In various embodiments,a location of the user may be determined using a location detectionservice, a merchant at the location may be determined, and whether themerchant at the location accepts the online payment provider may bedetermined. Thus, the informational element may comprise a notificationof whether the merchant accepts the online payment provider forpayments. In other embodiments, nearby merchants accepting the onlinepayment provider and merchant information for the nearby merchants usingthe location of the user may be determined, wherein the merchantinformation comprises offers for the nearby merchants and a notificationprovided as the at least one first informational element correspondingto the nearby merchants. For example, a predefined proximity surroundingthe user may define the nearby merchants and/or distance to search forthe nearby merchants.

In various embodiments, the at least one first informational element isdetermined based on an importance of the at least one informationalelement to the user, and wherein the importance is determined based onuser preferences for the user. The user preferences may be one of set byuser with the application, determined using user personal and financialinformation, and determined through use of the application by the user.The at least one first informational element is processed with the firstapplication icon, wherein the first application icon is processed todisplay the at least one first informational element with the firstgraphical element as a first customized application icon, at step 406.

At step 408, the first customized application icon is displayed througha graphical user interface of the computing device system. A selectionof the first application icon displaying the at least one firstinformational element may be received, and an interface of theapplication associated with the at least one first informational elementdisplayed with the first application icon may be automatically opened.Additionally, the at least one first informational element may be aplurality of informational elements, wherein the first customizedapplication icon automatically scrolls through the plurality ofinformation elements. In such embodiments, an interface of the firstapplication associated with the one of the plurality of informationalelements displayed with the first application icon may be automaticallyopened when the first customized application icon is selected having oneof the plurality of informational elements displayed.

In various embodiments, second application data for a second applicationexecutable by the computing device system is accessed, wherein thesecond application data comprises a second application icon for thesecond application and second application information displayed to theuser of the computing device system during use of the secondapplication, and wherein the second application icon comprises a secondgraphical element associated with the second application. At least onesecond informational element from the second application information fordisplay to the user is determined, wherein the at least one secondinformational element is determined using the at least one firstinformational element, and the at least one second information elementis displayed on at least one of the first customized application iconand a second customized application icon for the second application.Moreover, the at least one first informational element may be updated onthe first customized application icon based on newly receivedinformation by the computing device system. In other embodiments, atleast one second informational element of the first applicationinformation is determined based on at least one of user preferences,location information for the user, and user information. Thus, the firstcustomized application icon is updated with the at least one secondinformation element displayed with the first graphical element.

FIG. 5 is a block diagram of a computer system suitable for implementingone or more components in FIG. 1, according to an embodiment. In variousembodiments, the communication device may comprise a personal computingdevice (e.g., smart phone, a computing tablet, a personal computer,laptop, a wearable computing device such as glasses or a watch,Bluetooth device, key FOB, badge, etc.) capable of communicating withthe network. The service provider may utilize a network computing device(e.g., a network server) capable of communicating with the network. Itshould be appreciated that each of the devices utilized by users andservice providers may be implemented as computer system 500 in a manneras follows.

Computer system 500 includes a bus 502 or other communication mechanismfor communicating information data, signals, and information betweenvarious components of computer system 500. Components include aninput/output (I/O) component 504 that processes a user action, such asselecting keys from a keypad/keyboard, selecting one or more buttons,image, or links, and/or moving one or more images, etc., and sends acorresponding signal to bus 502. I/O component 504 may also include anoutput component, such as a display 511 and a cursor control 513 (suchas a keyboard, keypad, mouse, etc.). An optional audio input/outputcomponent 505 may also be included to allow a user to use voice forinputting information by converting audio signals. Audio I/O component505 may allow the user to hear audio. A transceiver or network interface506 transmits and receives signals between computer system 500 and otherdevices, such as another communication device, service device, or aservice provider server via network 150. In one embodiment, thetransmission is wireless, although other transmission mediums andmethods may also be suitable. One or more processors 512, which can be amicro-controller, digital signal processor (DSP), or other processingcomponent, processes these various signals, such as for display oncomputer system 500 or transmission to other devices via a communicationlink 518. Processor(s) 512 may also control transmission of information,such as cookies or IP addresses, to other devices.

Components of computer system 500 also include a system memory component514 (e.g., RAM), a static storage component 516 (e.g., ROM), and/or adisk drive 517. Computer system 500 performs specific operations byprocessor(s) 512 and other components by executing one or more sequencesof instructions contained in system memory component 514. Logic may beencoded in a computer readable medium, which may refer to any mediumthat participates in providing instructions to processor(s) 512 forexecution. Such a medium may take many forms, including but not limitedto, non-volatile media, volatile media, and transmission media. Invarious embodiments, non-volatile media includes optical or magneticdisks, volatile media includes dynamic memory, such as system memorycomponent 514, and transmission media includes coaxial cables, copperwire, and fiber optics, including wires that comprise bus 502. In oneembodiment, the logic is encoded in non-transitory computer readablemedium. In one example, transmission media may take the form of acousticor light waves, such as those generated during radio wave, optical, andinfrared data communications.

Some common forms of computer readable media includes, for example,floppy disk, flexible disk, hard disk, magnetic tape, any other magneticmedium, CD-ROM, any other optical medium, punch cards, paper tape, anyother physical medium with patterns of holes, RAM, PROM, EEPROM,FLASH-EEPROM, any other memory chip or cartridge, or any other mediumfrom which a computer is adapted to read.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by computer system 500. In various other embodiments of thepresent disclosure, a plurality of computer systems 500 coupled bycommunication link 518 to the network (e.g., such as a LAN, WLAN, PTSN,and/or various other wired or wireless networks, includingtelecommunications, mobile, and cellular phone networks) may performinstruction sequences to practice the present disclosure in coordinationwith one another.

Where applicable, various embodiments provided by the present disclosuremay be implemented using hardware, software, or combinations of hardwareand software. Also, where applicable, the various hardware componentsand/or software components set forth herein may be combined intocomposite components comprising software, hardware, and/or both withoutdeparting from the spirit of the present disclosure. Where applicable,the various hardware components and/or software components set forthherein may be separated into sub-components comprising software,hardware, or both without departing from the scope of the presentdisclosure. In addition, where applicable, it is contemplated thatsoftware components may be implemented as hardware components andvice-versa.

Software, in accordance with the present disclosure, such as programcode and/or data, may be stored on one or more computer readablemediums. It is also contemplated that software identified herein may beimplemented using one or more general purpose or specific purposecomputers and/or computer systems, networked and/or otherwise. Whereapplicable, the ordering of various steps described herein may bechanged, combined into composite steps, and/or separated into sub-stepsto provide features described herein.

The foregoing disclosure is not intended to limit the present disclosureto the precise forms or particular fields of use disclosed. As such, itis contemplated that various alternate embodiments and/or modificationsto the present disclosure, whether explicitly described or impliedherein, are possible in light of the disclosure. Having thus describedembodiments of the present disclosure, persons of ordinary skill in theart will recognize that changes may be made in form and detail withoutdeparting from the scope of the present disclosure. Thus, the presentdisclosure is limited only by the claims.

What is claimed is:
 1. A computing device system comprising: anon-transitory memory storing an application executable by the computingdevice system and application data for the application, wherein theapplication data comprises an application icon for the application andapplication information displayed to a user of the computing devicesystem during use of the application, and wherein the application iconcomprises a graphical element associated with the application; and oneor more hardware processors coupled to the non-transitory memory andconfigured to read instructions from the non-transitory memory to causethe system to perform operations comprising: accessing the applicationdata for the application; determining at least one informational elementfrom the application information for display to the user on theapplication icon of the application; processing the at least oneinformational element with the application icon, wherein the applicationicon is processed to display the at least one informational element withthe first graphical element as a customized application icon; anddisplaying the customized application icon through a graphical userinterface of the computing device system.